CVE-2025-48931
TeleMessage MD5 Password Hashing Weakness
Description
The TeleMessage service through 2025-05-05 relies on MD5 for password hashing, which opens up various attack possibilities (including rainbow tables) with low computational effort.
INFO
Published Date :
May 28, 2025, 5:15 p.m.
Last Modified :
Oct. 3, 2025, 2:32 p.m.
Remotely Exploit :
No
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source | 
|---|---|---|---|---|---|---|
| CVSS 3.1 | LOW | [email protected] | ||||
| CVSS 3.1 | MEDIUM | [email protected] | 
Solution
- Use bcrypt or scrypt for password hashing.
- Implement password hashing with a salt.
- Avoid using MD5 for password storage.
- Update the TeleMessage service.
References to Advisories, Solutions, and Tools
                                            Here, you will find a curated list of external links that provide in-depth
                                            information, practical solutions, and valuable tools related to
                                            CVE-2025-48931.
                                        
| URL | Resource | 
|---|---|
| https://www.wired.com/story/how-the-signal-knock-off-app-telemessage-got-hacked-in-20-minutes/ | Press/Media Coverage | 
CWE - Common Weakness Enumeration
            While CVE identifies
            specific instances of vulnerabilities, CWE categorizes the common flaws or
            weaknesses that can lead to vulnerabilities. CVE-2025-48931 is
            associated with the following CWEs:
        
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
            (CAPEC)
            stores attack patterns, which are descriptions of the common attributes and
            approaches employed by adversaries to exploit the CVE-2025-48931
            weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
			The following list is the news that have been mention
			CVE-2025-48931 vulnerability anywhere in the article.
		
                The following table lists the changes that have been made to the
                CVE-2025-48931 vulnerability over time.
            
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
- 
                            Initial Analysis by [email protected]Oct. 03, 2025 Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Added CPE Configuration OR *cpe:2.3:a:smarsh:telemessage:*:*:*:*:*:*:*:* versions up to (including) 2025-05-05 Added Reference Type MITRE: https://www.wired.com/story/how-the-signal-knock-off-app-telemessage-got-hacked-in-20-minutes/ Types: Press/Media Coverage 
- 
                            New CVE Received by [email protected]May. 28, 2025 Action Type Old Value New Value Added Tag exclusively-hosted-service Added Description The TeleMessage service through 2025-05-05 relies on MD5 for password hashing, which opens up various attack possibilities (including rainbow tables) with low computational effort. Added CVSS V3.1 AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N Added CWE CWE-328 Added Reference https://www.wired.com/story/how-the-signal-knock-off-app-telemessage-got-hacked-in-20-minutes/ 
 
                         
                         
                         
                                             
                                            